home *** CD-ROM | disk | FTP | other *** search
-
-
-
- GGGGRRRROOOOFFFFFFFF____MMMMSSSS((((7777)))) GGGGrrrrooooffffffff VVVVeeeerrrrssssiiiioooonnnn 1111....00009999 ((((00004444 MMMMaaaarrrrcccchhhh 1111999999994444)))) GGGGRRRROOOOFFFFFFFF____MMMMSSSS((((7777))))
-
-
-
- NNNNAAAAMMMMEEEE
- groff_ms - groff ms macros
-
- SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
- ggggrrrrooooffffffff ----mmmmggggssss [ _o_p_t_i_o_n_s... ] [ _f_i_l_e_s... ]
-
- DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
- This manual page describes the GNU version of the ms macros,
- which is part of the groff document formatting system. The
- groff ms macros are intended to be compatible with the
- documented behaviour of the 4.3 BSD Unix ms macros subject
- to the following limitations:
-
- o+ the internals of groff ms are not similar to the
- internals of Unix ms and so documents that depend upon
- implementation details of Unix ms may well not work
- with groff ms;
-
- o+ there is no support for typewriter-like devices;
-
- o+ Berkeley localisms, in particular the TTTTMMMM and CCCCTTTT macros,
- are not implemented;
-
- o+ groff ms does not provide cut marks;
-
- o+ multiple line spacing is not allowed (use a larger
- vertical spacing instead);
-
- o+ groff ms does not work in compatibility mode (eg with
- the ----CCCC option);
-
- o+ the error-handling policy of groff ms is to detect and
- report errors, rather than silently to ignore them.
-
- The groff ms macros make use of many features of GNU troff
- and therefore cannot be used with any other troff.
-
- Bell Labs localisms are not implemented in either the BSD ms
- macros or in the groff ms macros.
-
- Some Unix ms documentation says that the CCCCWWWW and GGGGWWWW number
- registers can be used to control the column width and gutter
- width respectively. This is not the case. These number
- registers are not used in groff ms.
-
- Macros that cause a reset set the indent. Macros that
- change the indent do not increment or decrement the indent,
- but rather set it absolutely. This can cause problems for
- documents that define additional macros of their own. The
- solution is to use not the iiiinnnn request but instead the RRRRSSSS and
- RRRREEEE macros.
-
-
-
-
- Page 1 (printed 7/8/94)
-
-
-
-
-
-
- GGGGRRRROOOOFFFFFFFF____MMMMSSSS((((7777)))) GGGGrrrrooooffffffff VVVVeeeerrrrssssiiiioooonnnn 1111....00009999 ((((00004444 MMMMaaaarrrrcccchhhh 1111999999994444)))) GGGGRRRROOOOFFFFFFFF____MMMMSSSS((((7777))))
-
-
-
- The number register GGGGSSSS is set to 1 by the groff ms macros,
- but is not used by the Unix ms macros. It is intended that
- documents that need to determine whether they are being
- formatted with Unix ms or groff ms make use of this number
- register.
-
- Footnotes are implemented so that they can safely be used
- within keeps and displays. Automatically numbered footnotes
- within floating keeps are not recommended. It is safe to
- have another \\\\******** between a \\\\******** and the corresponding ....FFFFSSSS; it
- is required only that each ....FFFFSSSS occur after the corresponding
- \\\\******** and that the occurrences of ....FFFFSSSS are in the same order as
- the corresponding occurrences of \\\\********.
-
- The strings \\\\****{{{{ and \\\\****}}}} can be used to begin and end a
- superscript.
-
- Some Unix V10 ms features are implemented. The BBBB, IIII and BBBBIIII
- macros can have an optional third argument which will be
- printed in the current font before the first argument.
- There is a macro CCCCWWWW like BBBB that changes to a constant-width
- font.
-
- The following strings can be redefined to adapt the groff ms
- macros to languages other than English:
-
- String Default Value
- REFERENCES References
- ABSTRACT ABSTRACT
- TOC Table of Contents
- MONTH1 January
- MONTH2 February
- MONTH3 March
- MONTH4 April
- MONTH5 May
- MONTH6 June
- MONTH7 July
- MONTH8 August
- MONTH9 September
- MONTH10 October
- MONTH11 November
- MONTH12 December
-
- The font family is reset from the string FFFFAAAAMMMM; at
- initialization if this string is undefined it is set to the
- current font family. The point size, vertical spacing, and
- inter-paragraph spacing for footnotes are taken from the
- number registers FFFFPPPPSSSS, FFFFVVVVSSSS, and FFFFPPPPDDDD; at initialization these
- are set to \\\\nnnn((((PPPPSSSS----2222, \\\\nnnn[[[[FFFFPPPPSSSS]]]]++++2222, and \\\\nnnn((((PPPPDDDD////2222 respectively;
- however, if any of these registers has been defined before
- initialization, it will not be set. The hyphenation flags
- (as set by the ....hhhhyyyy request) are set from the HHHHYYYY register; if
-
-
- Page 2 (printed 7/8/94)
-
-
-
-
-
-
- GGGGRRRROOOOFFFFFFFF____MMMMSSSS((((7777)))) GGGGrrrrooooffffffff VVVVeeeerrrrssssiiiioooonnnn 1111....00009999 ((((00004444 MMMMaaaarrrrcccchhhh 1111999999994444)))) GGGGRRRROOOOFFFFFFFF____MMMMSSSS((((7777))))
-
-
-
- this has not been defined at initialization, it will be set
- to 14.
-
- Right-aligned displays are available with ....DDDDSSSS RRRR and ....RRRRDDDD.
-
- The following conventions are used for names of macros,
- strings and number registers. External names available to
- documents that use the groff ms macros contain only
- uppercase letters and digits. Internally the macros are
- divided into modules. Names used only within one module are
- of the form _m_o_d_u_l_e****_n_a_m_e. Names used outside the module in
- which they are defined are of the form _m_o_d_u_l_e@@@@_n_a_m_e. Names
- associated with a particular environment are of the form
- _e_n_v_i_r_o_n_m_e_n_t::::_n_a_m_e; these are used only within the ppppaaaarrrr module,
- and _n_a_m_e does not have a module prefix. Constructed names
- used to implement arrays are of the form _a_r_r_a_y!!!!_i_n_d_e_x. Thus
- the groff ms macros reserve the following names:
-
- o+ names containing ****;
-
- o+ names containing @@@@;
-
- o+ names containing ::::;
-
- o+ names containing only uppercase letters and digits.
-
- FFFFIIIILLLLEEEESSSS
- ////uuuussssrrrr////sssskkkkuuuunnnnkkkk////lllliiiibbbb////ggggrrrrooooffffffff////ttttmmmmaaaacccc////ttttmmmmaaaacccc....ggggssss
-
- SSSSEEEEEEEE AAAALLLLSSSSOOOO
- ggggrrrrooooffffffff(1), ggggttttrrrrooooffffffff(1), ggggttttbbbbllll(1), ggggppppiiiicccc(1), ggggeeeeqqqqnnnn(1)
- mmmmssss(7)
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Page 3 (printed 7/8/94)
-
-
-
-